engine: consolidate network drivers documentation #23731
+963
−1,429
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: David Karlsson <[email protected]>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
bot
added
area/engine
robmry
approved these changes
Nov 17, 2025
Contributor
robmry
left a comment
robmry
left a comment
There was a problem hiding this comment.
LGTM - comments can be suggestions for follow-up.
Comment on lines
+475
to
+480
| 8. Clean up: | ||
|
|
||
| ```console | ||
| $ docker container stop alpine1 alpine2 | ||
| $ docker container rm alpine1 alpine2 | ||
| ``` |
Contributor
There was a problem hiding this comment.
Could add a "docker ps -a" between the stop and rm, to note that stopped containers lose their IP address etc?
Comment on lines
+423
to
+426
| 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 | ||
| link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 | ||
| inet 127.0.0.1/8 scope host lo | ||
| valid_lft forever preferred_lft forever |
Contributor
There was a problem hiding this comment.
Could update this to include the ::1 on lo (which will now be there unless IPv6 is disabled on the host, or by sysctl-ing the container).
aevesdocker
approved these changes
Nov 21, 2025
Contributor
aevesdocker
left a comment
aevesdocker
left a comment
There was a problem hiding this comment.
Picky style guide nits. Otherwise LGTM
| ## Usage example | ||
|
|
||
| This example shows how to start an nginx container that binds directly to port | ||
| 80 on the Docker host. From a networking perspective, this provides the same |
Contributor
There was a problem hiding this comment.
Suggested change
| 80 on the Docker host. From a networking perspective, this provides the same | |
| `80` on the Docker host. From a networking perspective, this provides the same |
|
|
||
| ## Usage example | ||
|
|
||
| This example shows how to start an nginx container that binds directly to port |
Contributor
There was a problem hiding this comment.
Suggested change
| This example shows how to start an nginx container that binds directly to port | |
| This example shows how to start an Nginx container that binds directly to port |
|
|
||
| This example shows how to start an nginx container that binds directly to port | ||
| 80 on the Docker host. From a networking perspective, this provides the same | ||
| level of isolation as if nginx were running directly on the host, but the |
Contributor
There was a problem hiding this comment.
Suggested change
| level of isolation as if nginx were running directly on the host, but the | |
| level of isolation as if Nginx were running directly on the host, but the |
|
|
||
| ### Prerequisites | ||
|
|
||
| - Port 80 must be available on the Docker host. To make nginx listen on a |
Contributor
There was a problem hiding this comment.
Suggested change
| - Port 80 must be available on the Docker host. To make nginx listen on a | |
| - Port `80` must be available on the Docker host. To make Nginx listen on a |
| ### Prerequisites | ||
|
|
||
| - Port 80 must be available on the Docker host. To make nginx listen on a | ||
| different port, see the [nginx image documentation](https://hub.docker.com/_/nginx/). |
Contributor
There was a problem hiding this comment.
Suggested change
| different port, see the [nginx image documentation](https://hub.docker.com/_/nginx/). | |
| different port, see the [Nginx image documentation](https://hub.docker.com/_/nginx/). |
| nginx | ||
| ``` | ||
|
|
||
| The default `ingress` publish mode means you can browse to port 80 on any |
Contributor
There was a problem hiding this comment.
Suggested change
| The default `ingress` publish mode means you can browse to port 80 on any | |
| The default `ingress` publish mode means you can browse to port `80` on any |
| $ docker network create -d overlay my-overlay | ||
| ``` | ||
|
|
||
| 2. Start a service using the overlay network, publishing port 80 to port 8080: |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Start a service using the overlay network, publishing port 80 to port 8080: | |
| 2. Start a service using the overlay network, publishing port `80` to port `8080`: |
| You need two Docker hosts that can communicate with each other with the | ||
| following ports open between them: | ||
|
|
||
| - TCP port 2377 |
Contributor
There was a problem hiding this comment.
Suggested change
| - TCP port 2377 | |
| - TCP port `2377` |
| following ports open between them: | ||
|
|
||
| - TCP port 2377 | ||
| - TCP and UDP port 7946 |
Contributor
There was a problem hiding this comment.
Suggested change
| - TCP and UDP port 7946 | |
| - TCP and UDP port `7946` |
|
|
||
| - TCP port 2377 | ||
| - TCP and UDP port 7946 | ||
| - UDP port 4789 |
Contributor
There was a problem hiding this comment.
Suggested change
| - UDP port 4789 | |
| - UDP port `4789` |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Conslidates the documentation on network drivers, which for some drivers is
currently split up into two separate pages:
This PR removes the separate tutorials page and incorporates the relevant
content into the main page.